Epigram 2:

Functions delay binding; data structures induce binding. Moral: Structure data late in the programming process.

Alan J. Perlis Wikipedia: Alan J. Perlis  

Epigrams on Programming, Sept., 1982

Epigram 3:

Syntactic sugar causes cancer of the semicolon.

Alan J. Perlis Wikipedia: Alan J. Perlis  

Epigrams on Programming, Sept., 1982

Epigram 5:

If a program manipulates a large amount of data, it does so in a small number of ways.

Alan J. Perlis Wikipedia: Alan J. Perlis  

Epigrams on Programming, Sept., 1982

Epigram 9:

It is better to have 100 functions operate on one data structure than 10 functions on 10 data structures.

Alan J. Perlis Wikipedia: Alan J. Perlis  

Epigrams on Programming, Sept., 1982

Epigram 11:

If you have a procedure with ten parameters, you probably missed some.

Alan J. Perlis Wikipedia: Alan J. Perlis  

Epigrams on Programming, Sept., 1982

Epigram 13:

If two people write exactly the same program, each should be put into microcode and then they certainly won’t be the same.

Alan J. Perlis Wikipedia: Alan J. Perlis  

Epigrams on Programming, Sept., 1982

Epigram 14:

In the long run every program becomes rococo — then rubble.

Alan J. Perlis Wikipedia: Alan J. Perlis  

Epigrams on Programming, Sept., 1982

Epigram 17:

If a listener nods his head when you’re explaining your program, wake him up.

Alan J. Perlis Wikipedia: Alan J. Perlis  

Epigrams on Programming, Sept., 1982

Epigram 18:

A program without a loop and a structured variable isn’t worth writing.

Alan J. Perlis Wikipedia: Alan J. Perlis  

Epigrams on Programming, Sept., 1982

Epigram 22:

A good system can’t have a weak command language.

Alan J. Perlis Wikipedia: Alan J. Perlis  

Epigrams on Programming, Sept., 1982